Skip to content

updating kubebuilder to 4.10.1#186

Open
acornett21 wants to merge 1 commit intooperator-framework:mainfrom
acornett21:update_kubebuilder
Open

updating kubebuilder to 4.10.1#186
acornett21 wants to merge 1 commit intooperator-framework:mainfrom
acornett21:update_kubebuilder

Conversation

@acornett21
Copy link
Contributor

Description of the change:

  • Updating k8s to 1.34 and kubebuilder to 4.10.1

Motivation for the change:

@acornett21 acornett21 requested review from camilamacedo86 and removed request for everettraven and grokspawn November 20, 2025 14:59
Signed-off-by: Adam D. Cornett <adc@redhat.com>
@acornett21 acornett21 added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 20, 2025
@acornett21
Copy link
Contributor Author

This update is blocked until the below is resolved, since we can't go backwards on urlib3 version and re-introduce CVE's that we already fix.

@acornett21
Copy link
Contributor Author

It seems there is a release for the linked issue, but it's hard to tell if it will be included in k8s 1.34.

@camilamacedo86
Copy link

If we bump to kubebuilder latest works with latest k8s and go version ?
Or will still the backport? Can we not adopt the latest version?

@acornett21
Copy link
Contributor Author

I need the python library k8s library to match the k8s go library major version. Right now this can't happen, due to the dependency issue mentioned.

If you're saying migrate to k8s 1.35 and the kubebuilder version that matches that, it might be possible. However, if go is past 1.25.3 that wouldn't be possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants